Skip to main content

This is a new service – your feedback will help us to improve it.

Newcastle-under-Lyme Borough Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

entity: 19206178

reference
T6-18\TPO0018_A6
name
tree-preservation-order

undefined

T6-18\TPO0018
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.235418 52.981669,-2.235370 52.981695,-2.235371 52.981723,-2.235381 52.981735,-2.235440 52.981753,-2.235587 52.981782,-2.235667 52.981803,-2.235766 52.981814,-2.235878 52.981834,-2.235988 52.981846,-2.236003 52.981876,-2.236018 52.981897,-2.236097 52.981999,-2.236354 52.982322,-2.236372 52.982342,-2.236386 52.982363,-2.236402 52.982395,-2.236412 52.982422,-2.236430 52.982448,-2.236441 52.982489,-2.236453 52.982566,-2.236463 52.982602,-2.236479 52.982634,-2.236497 52.982665,-2.236504 52.982685,-2.236521 52.982850,-2.236507 52.982880,-2.236495 52.982893,-2.236434 52.982918,-2.236401 52.982933,-2.236381 52.982944,-2.236379 52.983099,-2.236439 52.983163,-2.236526 52.983146,-2.236655 52.983117,-2.236629 52.983078,-2.236588 52.983009,-2.236562 52.982961,-2.236547 52.982927,-2.236544 52.982912,-2.236544 52.982875,-2.236553 52.982792,-2.236542 52.982741,-2.236503 52.982625,-2.236497 52.982561,-2.236487 52.982527,-2.236451 52.982431,-2.236418 52.982374,-2.236373 52.982312,-2.236343 52.982256,-2.236182 52.982055,-2.236156 52.982027,-2.236127 52.981999,-2.236116 52.981986,-2.236013 52.981847,-2.236018 52.981803,-2.235975 52.981796,-2.235974 52.981781,-2.235828 52.981750,-2.235418 52.981669)))
point
POINT (-2.236163 52.9824)
notes
entry-date
2026-07-28
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Newcastle-under-Lyme Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL